Comments
-
I confirm the issue is fixed. I'm going to close my ticket.
-
Looks like it is fixed. I turned these back on last night and so far it looks good. I'll give it at least until tonight, then I close my ticket as resolved.
-
Thanks for the confirmation! The back end folks deleted a deprecated DNS A record some months back without updating all of their firewalls to stop querying it. That too filled up logs for many days before they corrected it. Also sometimes I see several days if failure to contact the license servers. I wish they had better…
-
I opened a ticket and I also discovered the source of the issue. I do not have Capture Client licensed so I can't even open the tab to configure it. The issue comes from two default (not editable and not able to delete) address objects: ---- Found the source; Default Address objects that are NOT editable and can not be…
-
It appears that for the last few days captureclient.sonicwall.com does not resolve in DNS. Does anyone realize there is an issue?
-
I have the same question. Were you able to find a solution anywhere?
-
Do you have SonicWall switches connected to your 4700? I have seen something similar on the NSA-3700. It is currently under investigation by SonicWall. I have a gut feeling it is related to interaction with the switches that are being managed from the 3700. I have also seen variations if the issue in several previous…
-
I should add to my previous post that it is only the SonicWave devices that will not associate with my NSA-3700 after being unassociated from my NSA-3600. The SonicPoint devices were able to associate with the 3700.
-
How does licensing impact SonicWave devices that are firewall managed these days? I have several that are listed under my NSA-3600 as "Associated Devices". Some are near expiration, one recently expired. I don't seem to find a way to associate them with my new NSA-3700 even if I delete from the 3600 (tried with one of…